V9.0.5/bump #119
V9.0.5/bump #119
Conversation
WalkthroughThis update introduces version 9.0.5, adding SHA-512/256 cryptographic hashing support and enhancements to HTTP Digest Access Authentication, including new enums and factory classes. It also updates dependencies across projects to the latest versions, refactors CI workflows for improved maintainability, and makes minor Docker and environment configuration updates. Changes
Sequence Diagram(s)sequenceDiagram
participant Client
participant Server
participant DigestAuthHandler
participant DigestHashFactory
Client->>Server: Sends HTTP request with Digest Auth
Server->>DigestAuthHandler: Receives and processes request
DigestAuthHandler->>DigestHashFactory: Requests hash for specified DigestAlgorithm
DigestHashFactory-->>DigestAuthHandler: Returns hash (e.g., SHA-256, SHA-512/256)
DigestAuthHandler-->>Server: Validates credentials
Server-->>Client: Responds based on authentication result
sequenceDiagram
participant App
participant UnkeyedHashFactory
participant SHA512256
App->>UnkeyedHashFactory: CreateCryptoSha512Slash256()
UnkeyedHashFactory->>SHA512256: Instantiate SHA-512/256 algorithm
SHA512256-->>UnkeyedHashFactory: Returns instance
UnkeyedHashFactory-->>App: Provides SHA-512/256 hashing capability
Possibly related PRs
Poem
Tip ⚡️ Faster reviews with caching
Enjoy the performance boost—your workflow just got faster. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Pull Request Overview
This PR bumps the project version to 9.0.5 while updating Dockerfile configurations, GitHub Actions workflows, and NuGet package release notes to improve compatibility and streamline automation.
- Updated Dockerfile: Upgraded base and build images and introduced platform-specific directives.
- Improved workflows: Set all jobs to use ubuntu-24.04 and replaced custom steps with reusable workflows.
- NuGet release notes: Revised package release notes with version bump and additional details.
Reviewed Changes
Copilot reviewed 50 out of 50 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| .docfx/Dockerfile.docfx | Updates to base image, build image version, and platform specification adjustments. |
| .github/workflows/pipelines.yml | Upgraded Ubuntu runner versions and replaced custom job steps with reusable workflows. |
| .nuget/*/PackageReleaseNotes.txt | Updated NuGet package release notes with version bumps and additional release information. |
Comments suppressed due to low confidence (1)
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (and similar release note files):7
- The release notes include an outdated 'Version 9.0.4' entry below the updated 'Version 9.0.5' section; please update or remove it to ensure consistency in release information.
Version 9.0.4
| docfx build | ||
|
|
||
| FROM base AS final | ||
| FROM nginx:1.27.4-alpine AS final |
There was a problem hiding this comment.
[nitpick] Consider specifying '--platform=$BUILDPLATFORM' in the final stage for consistency with the build stage, unless this difference is intentional.
| FROM nginx:1.27.4-alpine AS final | |
| FROM --platform=$BUILDPLATFORM nginx:1.27.4-alpine AS final |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
♻️ Duplicate comments (4)
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt (1)
1-5: Streamline wording in ALM section.Duplicate of suggestion in the
Cuemon.Extensions.AspNetCore.Authenticationrelease notes. Simplify “Dependencies to latest and greatest with respect to TFMs” to “Dependencies updated for TFMs” or similar.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt (1)
1-5: Streamline wording in ALM section.Same as above: “Dependencies to latest and greatest with respect to TFMs” can be shortened to “Dependencies updated for TFMs” or “Updated dependencies for TFMs.”
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt (1)
1-5: Streamline wording in ALM section.Again, consider replacing “Dependencies to latest and greatest with respect to TFMs” with “Dependencies updated for TFMs” to reduce wordiness.
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt (1)
1-5: Streamline wording in ALM section.Consistent with other packages: shorten “Dependencies to latest and greatest with respect to TFMs” to “Dependencies updated for TFMs” for clarity.
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
🧹 Nitpick comments (53)
.nuget/Cuemon.Net/PackageReleaseNotes.txt (1)
5-5: Consider simplifying the wording in the ALM section.The phrase “CHANGED Dependencies to latest and greatest with respect to TFMs” is a bit verbose. You could shorten it to something like:
- “UPDATED dependencies for TFMs”
This keeps the intent clear while improving readability.
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt (1)
5-5: Simplify wording to reduce wordiness
The phrase “with respect to TFMs” can be shortened to “for TFMs” (or “regarding TFMs”) to improve readability. Consider applying this change here and across all similar entries to maintain consistency.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt (2)
1-2: Remove leading BOM and ensure consistent version header formatting.The first line begins with a zero-width BOM character (
U+FEFF), which can cause parsing issues in some tools. Please remove the BOM. Additionally, verify that theVersionheader style matches the existing convention (e.g., no colon followingVersionfor entries 9.0.x).Proposed diff:
- Version 9.0.5 + Version 9.0.5
5-5: Shorten the wording for clarity.The phrase “with respect to” is wordy. Consider a more concise alternative to improve readability.
Proposed diff:
-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- UPDATED dependencies for all supported TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1)
4-6: Simplify wording in the changelog bullet
The phrase “with respect to TFMs” is somewhat wordy. Consider shortening it to improve readability. For example:- # ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + # ALM + - CHANGED Dependencies to latest TFMsOr:
- - CHANGED Dependencies to latest and greatest with respect to TFMs + - CHANGED Updated dependencies across all TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)
5-5: Reduce wordiness in ALM description
The phrase “with respect to” is a bit verbose. Consider simplifying to improve clarity:- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data/PackageReleaseNotes.txt (2)
1-2: Review version header and availability section
The new Version 9.0.5 header and Availability line correctly follow the existing pattern. However, the file contains a BOM (invisible U+FEFF) at the very start—please remove it to prevent hidden characters in the text.
4-5: Refine wording in ALM change
The phrase “with respect to TFMs” is somewhat verbose. Consider shortening it to “for TFMs” to improve readability and conciseness.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Threading/PackageReleaseNotes.txt (1)
5-5: Nit: Simplify wording for brevity.
The phrase “with respect to” can be shortened to reduce wordiness.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1)
5-5: Simplify wording to reduce verbosity
The phrase "with respect to TFMs" is a bit wordy. Consider shortening line 5 to something like:- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies updated to latest TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core.App/PackageReleaseNotes.txt (1)
4-6: Consider simplifying wording
The phrase “Dependencies to latest and greatest with respect to TFMs” is wordy. For clarity and brevity, consider using something like:- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies updated for target framework monikers (TFMs)🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)
4-6: Refine wording to improve conciseness
The phrase “with respect to TFMs” is a bit wordy. Consider replacing it with “for TFMs” to streamline the entry.# ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + - CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt (2)
1-2: Ensure consistent version heading formatting.The new entry uses “Version 9.0.5” (no colon), while earlier entries sometimes use “Version: X.Y.Z”. Consider unifying all version headings (either with or without the colon) for consistency across the changelog.
4-5: Remove wordiness from ALM entry.The phrase “with respect to TFMs” adds unnecessary verbosity. Simplify the bullet for clarity and brevity. For example:
- # ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + # ALM + - CHANGED Dependencies updated to latest TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt (1)
1-6: Remove BOM and refine the change description.
The invisible BOM at the start (
Version 9.0.5) can cause parsing or diff noise—please remove it so the file cleanly begins withVersion 9.0.5.The line
- CHANGED Dependencies to latest and greatest with respect to TFMsis a bit wordy and inconsistent with typical release-note conventions. Consider tightening it to:
ALM
- CHANGED Dependencies to latest and greatest with respect to TFMs
ALM
- CHANGED Updated dependencies to the latest versions for all supported TFMs
<details> <summary>🧰 Tools</summary> <details> <summary>🪛 LanguageTool</summary> [uncategorized] ~5-~5: You might be missing the article “the” here. Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver... (AI_EN_LECTOR_MISSING_DETERMINER_THE) --- [style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative. Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET... (EN_WORDINESS_PREMIUM_WITH_RESPECT_TO) </details> </details> </blockquote></details> <details> <summary>.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1)</summary><blockquote> `5-5`: **Consider refining wording for conciseness** The phrase “with respect to TFMs” can feel verbose. You might shorten it to “for TFMs” or “across TFMs” to improve readability in the release notes. <details> <summary>🧰 Tools</summary> <details> <summary>🪛 LanguageTool</summary> [style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative. Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET... (EN_WORDINESS_PREMIUM_WITH_RESPECT_TO) </details> </details> </blockquote></details> <details> <summary>src/Cuemon.Core.App/Cuemon.Core.App.csproj (1)</summary><blockquote> `11-11`: **Suppress NU5128 warning**: The addition of `<NoWarn>NU5128</NoWarn>` correctly silences the packaging warning. To improve maintainability and avoid repeating this across multiple projects, consider centralizing common warning suppressions in a shared `Directory.Build.props`. </blockquote></details> <details> <summary>src/Cuemon.AspNetCore.App/Cuemon.AspNetCore.App.csproj (1)</summary><blockquote> `12-12`: **Suppress NU5128 warning**: Consistently adding `<NoWarn>NU5128</NoWarn>` here aligns with other project files. As a follow-up, you might consolidate such common properties into a `Directory.Build.props` to adhere to DRY principles. </blockquote></details> <details> <summary>.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt (2)</summary><blockquote> `1-1`: **Remove leading BOM for consistent rendering.** The first line appears to include a UTF-8 BOM character (`\uFEFF`) before "Version 9.0.5". This can introduce invisible characters in diffs or tooling. Please remove the BOM so the file begins directly with `Version 9.0.5`. --- `5-5`: **Shorten wording to improve conciseness.** The phrase "with respect to" is a bit verbose. Consider revising ```diff - CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest TFMsto keep the entry concise and clear.
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1)
4-6: Streamline ALM description wording.
The phrase “with respect to TFMs” is wordy; consider replacing it with “for TFMs” to improve readability.-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt (2)
1-2: Remove visible BOM marker
The leading “” character beforeVersion 9.0.5indicates a Byte-Order Mark. Removing the BOM will prevent stray characters from appearing in diffs and ensure compatibility with text-based tools.
5-5: Simplify changelog wording
The phrase “Dependencies to latest and greatest with respect to TFMs” is a bit verbose. Consider a more concise alternative, for example:
- “Updated dependencies to latest TFMs”
- “Dependencies updated to latest TFMs”
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt (2)
1-2: Remove BOM and confirm new version entry
The entry for Version 9.0.5 is accurate and follows the project's release-note pattern, but there’s a leading BOM character on line 1 (Version 9.0.5) that can introduce encoding issues in some tools. Please remove the BOM so the file remains plain ASCII/UTF-8 without hidden characters.
4-5: Refine wording for conciseness
The phrase “with respect to TFMs” is somewhat verbose. Consider shortening it to “for TFMs” to improve readability and maintain consistency with other notes.Proposed diff:
# ALM -CHANGED Dependencies to latest and greatest with respect to TFMs +CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)
4-5: Consider simplifying the ALM description.
The phrase “Dependencies to latest and greatest with respect to TFMs” is a bit wordy. For consistency and brevity, you might revise it to something like:- # ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + # ALM + - CHANGED Dependencies to latest TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (2)
1-1: Remove BOM at start of file.
The hidden byte-order-mark () before “Version 9.0.5” can cause encoding or parsing issues in tools.
Apply this diff to remove it:- Version 9.0.5 + Version 9.0.5
4-5: Shorten “with respect to” for clarity.
The phrase “with respect to TFMs” is a bit wordy and has been flagged by style tooling. Consider simplifying to “across all TFMs” or similar.
Example diff:- # ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + # ALM + - CHANGED Dependencies updated to latest versions across all TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt (1)
1-5: Streamline wording in ALM section.The phrase “Dependencies to latest and greatest with respect to TFMs” is a bit verbose. Consider simplifying to “Dependencies updated for TFMs” or “Updated dependencies for TFMs” to improve readability and consistency across release notes.
🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.IO/PackageReleaseNotes.txt (1)
5-5: Consider refining wording for clarity.
The phrasing “Dependencies to latest and greatest with respect to TFMs” is a bit wordy. Suggest adding “the” and simplifying:- # ALM - - CHANGED Dependencies to latest and greatest with respect to TFMs + # ALM + - CHANGED Dependencies to the latest versions for all supported TFMs🧰 Tools
🪛 LanguageTool
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.docfx/Dockerfile.docfx (2)
11-11: Consider adding platform flag to final stage for consistency
If you intend the final image to also target multiple architectures, you could include--platform=$BUILDPLATFORMhere.Apply this diff for consistency:
-FROM nginx:1.27.4-alpine AS final +FROM --platform=$BUILDPLATFORM nginx:1.27.4-alpine AS final
6-6: Use COPY instead of ADD for static folders
Per best practices (Hadolint DL3020), preferCOPY [".", "docfx"]here to avoid the extra layer semantics ofADD.Apply this diff:
- ADD [".", "docfx"] + COPY [".", "docfx"]🧰 Tools
🪛 Hadolint (2.12.0)
[error] 6-6: Use COPY instead of ADD for files and folders
(DL3020)
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (1)
5-5: Reduce wordiness in ALM description
The phrase “with respect to” is somewhat verbose. Consider simplifying to “for TFMs” to improve readability and consistency across release notes.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)
5-5: Streamline ALM change note
To reduce redundancy, you might replace “with respect to TFMs” with a shorter phrase like “for TFMs.”- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)
5-5: Nit: simplify wording in ALM section
The wording “with respect to TFMs” can be tightened to “for TFMs” for brevity.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (1)
5-5: Refine ALM description for clarity
Consider replacing “with respect to TFMs” with “for TFMs” to reduce verbosity.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1)
5-5: Simplify ALM note wording
The phrase “with respect to TFMs” can be shortened to “for TFMs” for consistency and readability.- CHANGED Dependencies to latest and greatest with respect to TFMs + CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (1)
5-5: Consider simplifying the wording.
The phrase “with respect to TFMs” is a bit verbose; you might use “for TFMs” or “to update TFMs” for brevity.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1)
5-5: Nitpick: streamline the phrasing.
Consider replacing “with respect to TFMs” with “for TFMs” to make it more concise.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1)
5-5: Style suggestion: concise wording.
The wording “with respect to TFMs” could be shortened to “for TFMs” to improve readability.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (1)
5-5: Minor wording refinement.
To reduce wordiness, replace “with respect to TFMs” with “for TFMs” or “to TFMs”.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core/PackageReleaseNotes.txt (1)
5-5: Optional: shorten phrasing.
Consider using “for TFMs” instead of “with respect to TFMs” to make the line more concise.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (2)
5-5: Consider shortening “with respect to TFMs.”
The phrase “with respect to” is wordy. You could use “for TFMs” or “across TFMs” to make it more concise.Example diff:
-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # New Features - ADDED SecureHas...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
8-9: Typo: duplicate “a”.
Line 8 reads “provides a a SHA-512-256…”. Removing the extra “a” will fix the typo.Example diff:
- ADDED SecureHashAlgorithm512256 class in the Cuemon.Security.Cryptography namespace that provides a a SHA-512-256 implementation… + ADDED SecureHashAlgorithm512256 class in the Cuemon.Security.Cryptography namespace that provides a SHA-512-256 implementation…🧰 Tools
🪛 LanguageTool
[duplication] ~8-~8: Possible typo: you repeated a word.
Context: ...ty.Cryptography namespace that provides a a SHA-512-256 implementation of the SHA (...(ENGLISH_WORD_REPEAT_RULE)
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (2)
5-5: Simplify “with respect to TFMs.”
As above, consider replacing with “for TFMs” to improve readability.Example diff:
-# ALM -- CHANGED Dependencies to latest and greatest with respect to TFMs +# ALM +- CHANGED Dependencies to latest and greatest for TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # New Features - ADDED DigestCry...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
15-17: Add missing article “the” before “newly added.”
Each bug-fix line should read “…to use the newly added DigestCryptoAlgorithm enum…”.Example diff:
- FIXED DigestAuthenticationHandler class … to use newly added DigestCryptoAlgorithm enum in the Cuemon.AspNetCore.Authentication.Digest namespace + FIXED DigestAuthenticationHandler class … to use the newly added DigestCryptoAlgorithm enum in the Cuemon.AspNetCore.Authentication.Digest namespace(Apply similarly for lines 16–17.)
🧰 Tools
🪛 LanguageTool
[uncategorized] ~15-~15: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~16-~16: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~17-~17: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...(AI_EN_LECTOR_MISSING_DETERMINER_THE)
CHANGELOG.md (5)
9-11: Enhance summary to reflect key feature additions
The description “service update that focuses on package dependencies and a few bug fixes” is too generic given the major additions of SHA-512/256 support and HTTP Digest enhancements. Please update this summary to highlight the new cryptographic algorithm and digest authentication features.
18-18: Improve code formatting in description
Wrap type names in backticks and use<TAlgorithm>for generics. For example:
- `UnkeyedCryptoHash` instead of UnkeyedCryptoHash{TAlgorithm}
22-23: Consider naming consistency for SHA-512/256 enum and factory
The enum valueSha512Slash256and methodCreateCryptoSha512Slash256use "Slash" to denote "/". This may be confusing compared to other values likeSha256orSha384. Consider renaming toSha512256orSha512_256for clarity and consistency in theUnkeyedCryptoAlgorithmenum and corresponding factory method.
24-24: Clarify digest option property entry
Please wrapDigestAlgorithmand its defaultDigestCryptoAlgorithm.Sha256in backticks to clearly denote code elements. This improves readability.
28-30: Consolidate repetitive fix entries
The three fix bullets for handler, middleware, and header builder all reference the same change (using the newDigestCryptoAlgorithmenum). Consider merging into a single bullet with a comma-separated list of impacted classes to keep the changelog concise..nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt (2)
1-1: Remove leading BOM character.
The first line begins with a hidden zero-width no-break space (BOM) before “Version”. This can confuse some parsers and editors—please delete the BOM so the line starts cleanly withVersion 9.0.5.
5-5: Simplify wording in change description.
The phrase “with respect to TFMs” is a bit verbose. Consider shortening to something like “for TFMs” or “across TFMs” to improve readability.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (50)
.docfx/Dockerfile.docfx(1 hunks).github/workflows/pipelines.yml(7 hunks).nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Core.App/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Core/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Data/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.IO/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Net/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Resilience/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Threading/PackageReleaseNotes.txt(1 hunks).nuget/Cuemon.Xml/PackageReleaseNotes.txt(1 hunks)CHANGELOG.md(1 hunks)Directory.Packages.props(2 hunks)src/Cuemon.AspNetCore.App/Cuemon.AspNetCore.App.csproj(1 hunks)src/Cuemon.Core.App/Cuemon.Core.App.csproj(1 hunks)src/Cuemon.Security.Cryptography/SHA512256.cs(1 hunks)testenvironments.json(1 hunks)
🧰 Additional context used
🪛 LanguageTool
.nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Xml/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Net/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core.App/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Reflection/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.DependencyInjection/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Razor.TagHelpers/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Core/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.RazorPages/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Text.Json/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Data.Integrity/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Xml/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Threading/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.IO/PackageReleaseNotes.txt
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.IO/PackageReleaseNotes.txt
[uncategorized] ~5-~5: You might be missing the article “the” here.
Context: ...d 2.0 # ALM - CHANGED Dependencies to latest and greatest with respect to TFMs Ver...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Runtime.Caching/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt
[style] ~11-~11: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.3 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Resilience/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Net/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Authentication/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # New Features - ADDED SecureHas...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[duplication] ~8-~8: Possible typo: you repeated a word.
Context: ...ty.Cryptography namespace that provides a a SHA-512-256 implementation of the SHA (...
(ENGLISH_WORD_REPEAT_RULE)
.nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs # New Features - ADDED DigestCry...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
[uncategorized] ~15-~15: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~16-~16: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
[uncategorized] ~17-~17: You might be missing the article “the” here.
Context: ....Authentication.Digest namespace to use newly added DigestCryptoAlgorithm enum in the...
(AI_EN_LECTOR_MISSING_DETERMINER_THE)
🪛 Hadolint (2.12.0)
.docfx/Dockerfile.docfx
[error] 6-6: Use COPY instead of ADD for files and folders
(DL3020)
🪛 YAMLlint (1.35.1)
.github/workflows/pipelines.yml
[warning] 285-285: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
⏰ Context from checks skipped due to timeout of 90000ms (7)
- GitHub Check: 🛠️ Build (Release, net8.0)
- GitHub Check: 🛠️ Build (Release, netstandard2.0)
- GitHub Check: 🛠️ Build (Debug, net8.0)
- GitHub Check: 🛠️ Build (Release, net9.0)
- GitHub Check: 🛠️ Build (Debug, net9.0)
- GitHub Check: 🛠️ Build (Debug, netstandard2.0)
- GitHub Check: 🪟 Prepare Windows
🔇 Additional comments (46)
.nuget/Cuemon.Extensions.Collections.Specialized/PackageReleaseNotes.txt (1)
1-3: Package release notes entry for v9.0.5 is accurate
Documenting the new version and supported TFMs (.NET 9, .NET 8, and .NET Standard 2.0) aligns with the pattern used across other Cuemon packages..nuget/Cuemon.Extensions.Threading/PackageReleaseNotes.txt (1)
1-2: Release notes entry added for version 9.0.5
The new version header and availability section correctly reflect the bump to 9.0.5 and maintain consistency with other entries..nuget/Cuemon.Threading/PackageReleaseNotes.txt (2)
1-2: Release entry header looks good.
The new version and availability specifiers align with the existing format and target frameworks.
4-4: ALM section header is consistent.
The# ALMheading matches previous entries and correctly groups the change list..nuget/Cuemon.Extensions.AspNetCore.Xml/PackageReleaseNotes.txt (1)
1-4: Release notes entry for 9.0.5 added correctly
The new version header, availability lines, and ALM section align with the existing style and match the coordinated updates across other packages..nuget/Cuemon.Core.App/PackageReleaseNotes.txt (1)
1-2: New version entry is consistent
The header and availability lines accurately follow the format of previous versions and correctly introduce version 9.0.5..nuget/Cuemon.Extensions.AspNetCore.Mvc.Formatters.Text.Json/PackageReleaseNotes.txt (1)
1-3: Release notes formatting is correct
The new version header and availability lines follow the established pattern and accurately reflect support for .NET 9 and .NET 8..nuget/Cuemon.Runtime.Caching/PackageReleaseNotes.txt (1)
1-6: Release notes version bump verified
The new entry for Version 9.0.5 correctly follows the existing format, lists the supported TFMs, and documents the dependency updates. No discrepancies or missing items detected.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Collections.Generic/PackageReleaseNotes.txt (1)
1-6: Approve new release notes entry and version bump.
The entry for Version 9.0.5 accurately reflects the updated dependency changes and follows the established format for TFMs support.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.Diagnostics/PackageReleaseNotes.txt (1)
1-2: Release note entry aligns with existing version format.
The new Version 9.0.5 declaration and its availability targets match the pattern of previous entries..nuget/Cuemon.Extensions.Data/PackageReleaseNotes.txt (1)
1-2: Release entry looks correct.
The new version header and availability line align with the existing 9.x entries and correctly list supported TFMs..nuget/Cuemon.IO/PackageReleaseNotes.txt (1)
1-2: Confirm version bump in release notes.
The new entry for Version 9.0.5 and its availability across .NET 9, .NET 8, .NET Standard 2.1, and .NET Standard 2.0 correctly reflects the updated package support.src/Cuemon.Security.Cryptography/SHA512256.cs (1)
1-21: Comprehensive file header documentation.
The added header block delivers clear attribution, specification references, and gratitude notes. This enhances maintainability and provides essential context for the SHA-512/256 implementation.Directory.Packages.props (4)
23-23: Approve xunit.runner.visualstudio version bump.
Updating to 3.1.0 aligns with the latest test tooling.
26-26: Approve Microsoft.Data.Sqlite update for net4.
Bumping to 8.0.16 ensures consistency with other TFMs.
38-38: Approve Microsoft.Data.Sqlite update for net8/netstandard2.
Aligns the net8 and netstandard2 configurations to 8.0.16.
46-51: Approve package version bumps for net9 TFMs.
All six packages correctly incremented from 9.0.4 to 9.0.5, maintaining consistency with the new release..github/workflows/pipelines.yml (8)
21-23: Minimal permissions: contents read.
Adding a top-levelcontents: readpermission tightens security by adhering to the principle of least privilege.
27-27: Update runner for Linux preparation.
Switchingruns-ontoubuntu-24.04ensures compatibility with the latest environment.
69-69: Update runner for build job.
Building onubuntu-24.04matches the other Linux workflows and reduces divergences.
191-191: Align test matrix with new Ubuntu version.
The test job now coversubuntu-24.04, replacing the older image.
239-239: Update SonarCloud runner.
Running analysis onubuntu-24.04keeps consistency across CI jobs.
283-290: Refactor Codecov to reusable workflow.
Delegating tocodebeltnet/jobs-codecovsimplifies maintenance and centralizes coverage logic.🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 285-285: too few spaces after comma
(commas)
294-297: Enhance CodeQL permissions and runner.
Switching toubuntu-24.04and addingsecurity-events: writeimproves analysis accuracy and security posture.
333-343: Delegate deploy to reusable workflow.
Usingcodebeltnet/jobs-nugetwith explicitcontents: writeandpackages: writepermissions streamlines the release process.🧰 Tools
🪛 YAMLlint (1.35.1)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
[warning] 334-334: too few spaces after comma
(commas)
testenvironments.json (1)
12-12: Approve Docker test image update.
Bumping thedockerImagetomono-net8.0.409-9.0.300aligns the test runner with the updated frameworks..docfx/Dockerfile.docfx (2)
1-1: Excellent: Base image updated for multi-platform and version bump
TheFROM --platform=$BUILDPLATFORM nginx:1.27.4-alpine AS baseensures we’re pulling the new 1.27.4-alpine image with explicit platform support, which is correct.
4-4: Good: Build stage image bumped with platform flag
Updating tocodebeltnet/docfx:2.78.3and specifying--platform=$BUILDPLATFORMmaintains consistency and multi-arch support..nuget/Cuemon.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
1-6: Release notes added for version 9.0.5
The new entry correctly documents availability on .NET 9/.NET 8 and the ALM change.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore.Mvc/PackageReleaseNotes.txt (1)
1-6: Release notes added for version 9.0.5
The new version block is correctly inserted, matching the pattern of other Cuemon packages.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore.App/PackageReleaseNotes.txt (1)
1-6: Release notes added for version 9.0.5
This new block correctly matches the pattern of other package release notes.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Extensions.AspNetCore/PackageReleaseNotes.txt (1)
1-2: Consistent versioning and availability
The new “Version 9.0.5” entry and its availability for .NET 9 and .NET 8 align with the other packages and follow the established format..nuget/Cuemon.Xml/PackageReleaseNotes.txt (1)
1-2: Approve new version entry
The addition of “Version 9.0.5” and its availability (.NET 9, .NET 8, .NET Standard 2.0) is correctly formatted and consistent with the overall release..nuget/Cuemon.Extensions.Xml/PackageReleaseNotes.txt (1)
1-2: Approve version and target TFMs
“Version 9.0.5” and its TFM availability (.NET 9, .NET 8, .NET Standard 2.0) are correctly added and mirror the other packages..nuget/Cuemon.Extensions.Text/PackageReleaseNotes.txt (1)
1-2: Approve release note header
The header for version 9.0.5 and its availability are accurate and consistent..nuget/Cuemon.Data.SqlClient/PackageReleaseNotes.txt (1)
1-2: Approve version bump
The new entry for “Version 9.0.5” and its supported frameworks (.NET 9, .NET 8, .NET Standard 2.0) is in line with the other packages..nuget/Cuemon.Extensions.Text.Json/PackageReleaseNotes.txt (1)
1-6: Release notes version bump looks good.
The new entry for Version 9.0.5 correctly lists target frameworks and documents the ALM change.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Diagnostics/PackageReleaseNotes.txt (1)
1-6: Release notes update for Version 9.0.5 is accurate.
The new version entry correctly specifies availability and the ALM dependency update.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Data.Integrity/PackageReleaseNotes.txt (1)
1-6: Version 9.0.5 entry is correct.
Target frameworks and the ALM change are appropriately documented.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.AspNetCore/PackageReleaseNotes.txt (1)
1-6: Version 9.0.5 release note is proper.
The availability (.NET 9 and .NET 8) and dependency update are correctly captured.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Core/PackageReleaseNotes.txt (1)
1-6: New version entry is correctly formatted.
Version 9.0.5 and its ALM dependency update align with the coordinated bump.🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
.nuget/Cuemon.Security.Cryptography/PackageReleaseNotes.txt (2)
1-2: New version header is formatted correctly.
The “Version 9.0.5” and availability lines clearly communicate the release scope.
12-13: Enum and factory extension documented clearly.
The entries for extendingUnkeyedCryptoAlgorithmandUnkeyedHashFactoryalign with the feature set introduced..nuget/Cuemon.AspNetCore.Authentication/PackageReleaseNotes.txt (3)
1-2: Release header is correct.
“Version 9.0.5” and availability lines accurately reflect supported TFMs.
8-9: New feature entries look good.
The additions ofDigestCryptoAlgorithmandDigestHashFactoryare documented accurately.
12-12: Improvement entry is clear.
ExtendingDigestAuthenticationOptionswith the newDigestAlgorithmproperty is well described.
| Version 9.0.5 | ||
| Availability: .NET 9, .NET 8 and .NET Standard 2.0 | ||
|
|
||
| # ALM | ||
| - CHANGED Dependencies to latest and greatest with respect to TFMs | ||
|
|
There was a problem hiding this comment.
💡 Verification agent
🧩 Analysis chain
Verify project file version bump.
The release notes announce version 9.0.5—please ensure that the corresponding .csproj or .nuspec for Cuemon.Extensions.Runtime.Caching has its <Version> set to 9.0.5 to stay in sync with these notes.
🏁 Script executed:
#!/usr/bin/env bash
# List all csproj files updated to Version 9.0.5
rg -l '<Version>9\.0\.5</Version>' -g '*.csproj'Length of output: 50
🏁 Script executed:
#!/usr/bin/env bash
# Locate all .csproj files with a <Version> element
echo "🔍 Scanning .csproj files for <Version> entries..."
rg -n '<Version>' -g '*.csproj'
# Locate all .nuspec files with a <version> element
echo -e "\n🔍 Scanning .nuspec files for <version> entries..."
rg -n '<version>' -g '*.nuspec'Length of output: 444
🏁 Script executed:
#!/usr/bin/env bash
# Include hidden directories (like .nuget) in the search
echo "🔍 Searching for .csproj files with <Version> tags (including hidden dirs)..."
rg -n --hidden '<Version>' -g '*.csproj'
echo -e "\n🔍 Searching for .nuspec files with <version> tags (including hidden dirs)..."
rg -n --hidden '<version>' -g '*.nuspec'
echo -e "\n📂 Listing all .csproj and .nuspec files in the repo (including hidden dirs)..."
find . -type f \( -name "*.csproj" -o -name "*.nuspec" \)Length of output: 6585
🏁 Script executed:
#!/usr/bin/env bash
# Search for any explicit '9.0.5' occurrences
echo "🔍 Searching for '9.0.5' across all files..."
rg -n '9\.0\.5'
# Check for PackageVersion in .csproj files
echo -e "\n🔍 Searching for <PackageVersion> in .csproj files..."
rg -n '<PackageVersion>' -g '*.csproj'
# Check for VersionPrefix in props files
echo -e "\n🔍 Searching for <VersionPrefix> in .props files..."
rg -n '<VersionPrefix>' -g '*.props'
# List any central props files that might declare the version
echo -e "\n🔍 Listing central props files (Directory.*.props):"
find . -type f -name 'Directory.*.props'Length of output: 1459
🏁 Script executed:
#!/usr/bin/env bash
# Display version settings in Directory.Build.props
echo "🔍 Extracting version properties from Directory.Build.props..."
rg -n '<Version>' -n '<VersionPrefix>' Directory.Build.props
echo -e "\n🔍 Checking for explicit <Version> in the Runtime.Caching project file..."
rg -n '<Version>' src/Cuemon.Extensions.Runtime.Caching/Cuemon.Extensions.Runtime.Caching.csproj || echo "No <Version> in csproj"Length of output: 570
Bump central package version to 9.0.5
I didn’t find an explicit <Version> in src/Cuemon.Extensions.Runtime.Caching/Cuemon.Extensions.Runtime.Caching.csproj—this project inherits its version from your central props. Please update your version property in Directory.Build.props (or whichever props file defines <Version>/<VersionPrefix>) to 9.0.5 so it matches your release notes:
• File: Directory.Build.props
<PropertyGroup>
<!-- ensure this is set or updated -->
<Version>9.0.5</Version>
<!-- if you use VersionPrefix instead: -->
<VersionPrefix>9.0.5</VersionPrefix>
</PropertyGroup>🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
There was a problem hiding this comment.
Actionable comments posted: 0
🧹 Nitpick comments (1)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1)
5-5: Consider reducing wordiness
The phrase “with respect to” could be shortened for clarity. For example:
- CHANGED Dependencies to latest TFMs🧰 Tools
🪛 LanguageTool
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (2)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt(1 hunks)CHANGELOG.md(1 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
- CHANGELOG.md
🧰 Additional context used
🪛 LanguageTool
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt
[style] ~5-~5: ‘with respect to’ might be wordy. Consider a shorter alternative.
Context: ...GED Dependencies to latest and greatest with respect to TFMs Version 9.0.4 Availability: .NET...
(EN_WORDINESS_PREMIUM_WITH_RESPECT_TO)
🔇 Additional comments (1)
.nuget/Cuemon.Extensions.Hosting/PackageReleaseNotes.txt (1)
1-2: Add new 9.0.5 version entry
The Version 9.0.5 header and its availability specification align with the existing release note structure and correctly document the bump to .NET 9, .NET 8, and .NET Standard 2.0.
|
This pull request includes updates to Dockerfile configurations, GitHub Actions workflows, and NuGet package release notes. Key changes focus on improving compatibility, updating dependencies, and streamlining workflows.
Dockerfile Updates:
.docfx/Dockerfile.docfxto usenginx:1.27.4-alpinewith platform-specific builds for enhanced compatibility.GitHub Actions Workflow Improvements:
runs-onenvironments in.github/workflows/pipelines.ymlto useubuntu-24.04for all jobs, ensuring compatibility with newer Ubuntu versions. [1] [2] [3] [4] [5] [6] [7]contents: readfor pipeline preparation andsecurity-events: writefor CodeQL analysis. [1] [2]codecovanddeployjobs with reusable workflows (codebeltnet/jobs-codecovandcodebeltnet/jobs-nuget) to simplify maintenance and improve consistency. [1] [2]NuGet Package Release Notes:
9.0.5, highlighting dependency updates, new features (e.g.,DigestCryptoAlgorithmenum), and bug fixes in theCuemon.AspNetCore.Authenticationpackage. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18]Summary by CodeRabbit
New Features
Bug Fixes
Chores
Documentation